Ticket tracking and redeeming system and method

ABSTRACT

An automated method and system for facilitating timely use and/or redemption of the unused portion of an electronic ticket are provided. In accordance with the method, ticket data (e.g., from an electronic ticket) is collected from a financial transaction account, then a search engine uses said ticket data to find open tickets. Finding open tickets includes setting an aging period and adding it to the scheduled departure date of the issued ticket, and a reminder period is set and subtracted from the scheduled date of a ticket. If the scheduled departure date plus the aging date is earlier than the current date, a determination is made as to whether the ticket has been used. If the scheduled date minus the reminder period is earlier than the current date, then a message is communicated to the traveler reminding him to use or redeem the ticket. A residual value of the ticket is calculated and list of open tickets with a value related to each ticket is transmitted to the issuing agency to facilitate the issuing agency issuing a refund of the open ticket.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a Continuation-in-Part, and claims benefit of, andpriority to, U.S. Non-provisional patent application Ser. No.10/294,930, filed Nov. 14, 2002, which claims priority to U.S.Provisional Patent Application Serial No. 60/396,224, filed on Jul. 15,2002; which application is a Continuation-in-Part, claims benefit of,and priority to U.S. Non-provisional Patent Application Ser. No.09/346,085, filed Jul. 1, 1999, all of which are hereby incorporated byreference.

FIELD OF INVENTION

This invention relates generally to a method and system for tracking andrefunding tickets, and more specifically to a method and system forcreating a list or report of refundable tickets in order to facilitatean issuing agency (e.g., travel agent) to obtain a refund for a client.

BACKGROUND OF INVENTION

The number of tickets being issued for services (such as airline andother forms of travel as well as hotel accommodations, concerts,seminars, shows, park admissions, events and the like) is rapidlyincreasing. It is especially true that the number of electronic tickets,and specifically electronic tickets for airline travel, is increasingvery rapidly. Many travelers, and especially frequent businesstravelers, find themselves in the position of scheduling many trips,changing itineraries, canceling or rescheduling trips, and otherwisecreating a complex history of travel scheduling and rescheduling. It isnot unusual in the midst of this hectic travel history to forget, orlose track, unused tickets. The problem of forgetting to timely use suchtickets and/or forgetting to redeem unused tickets is exacerbated by thegrowing use of electronic tickets, since, with the electronic ticket,the traveler may have no paper record to remind him or her when to use aticket or even that a ticket ever existed.

Unfortunately, unused and forgotten tickets expire after some prescribedperiod of time. If forgotten and unclaimed after expiration, the moneypaid for the ticket is usually kept by the airline or other serviceprovider, and no benefit is ever realized by the purchaser. If a numberof unused but paid for tickets expire and are not refunded or redeemed,a frequent traveler or a business that employs one or more travelers cansustain a significant financial loss and/or fail to capitalize onvaluable opportunity.

If the tickets are refundable, some of this loss may be recovered bytracking unused tickets and seeking refunds. But such refunds typicallymust be sought in a timely manner. For example, full or partial refundsmay be available prior to a specific date, but may be severely limitedafter such date. Even if the tickets are not refundable, they maynevertheless be redeemable for some form of value. In such cases, theloss may be mitigated through redemption of the unused tickets. Theimportance of this latter situation is becoming increasingly importantbecause, while the use of electronic tickets is growing, so is the useof non-refundable tickets. This trend is due in large part to thesignificant cost savings associated with non-refundable tickets, whichis causing their increased use by business travelers. Unfortunately, torecapture value from an unused, non-refundable ticket usually requires acumbersome alternative to a refund such as an exchange, a credit, adiscount, or some other mechanism for redeeming the ticket to captureits residual value. In addition, the window during which value may becaptured from an unused ticket typically does not remain openindefinitely, and the value that may be recaptured tends to decreasewith the passage of time. Accordingly, although it is typicallypreferable to use a ticket as scheduled, the next best option istypically to redeem an unused ticket as soon as possible, preferablybefore the scheduled date of the ticket.

In the past there has been no efficient way to track pending and/orunused tickets and to facilitate their use and/or their redemption forvalue on behalf of the traveler or the traveler's employer. Any systemsthat have been available have been substantially manual systems that areunreliable and have little ability to track current or past activity orto report on tickets that need to be used, that were actually redeemed,or that were not redeemed. Accordingly, a need existed for an automatedsystem for identifying soon to expire tickets and unused tickets thathave not been redeemed for value, for determining what form ofredemption may be used, and for communicating, to the appropriate partysuch as the ticket holder, appropriate information to facilitate use ofthe tickets or the issuance of redemption credit or exchange.

Furthermore, if a traveler purchases an electronic or paper ticket froman issuing agency (e.g., travel agent), according to ARC restrictions,any refund related to the ticket must be issued by the same issuingagency. For example, when a traveler purchases a ticket using afinancial transaction account (e.g., charge card), wherein the chargecard used to purchase the ticket is issued by the same entity thatissues the ticket, it is often easier for the charge card issuer toobtain a refund for the client. However, when a traveler purchases aticket from an issuing agency, but the traveler uses an unrelatedfinancial transaction account (e.g., charge card), the traveler is notable to obtain a refund directly from the host of the transactionaccount. Accordingly, a need exists for a system which automaticallynotifies a third party issuing agency of unused tickets purchased withan unrelated charge card.

SUMMARY OF INVENTION

The present invention overcomes the shortcomings and disadvantages ofthe prior art by facilitating the automated redemption of an unusedticket. The invention includes, in one embodiment, collecting ticketdata from a financial transaction account (e.g., charge card account),wherein the ticket data is used to determine issued tickets for selectedcard members, and sending the ticket data to a search engine to findopen tickets. The system may find open tickets by setting an agingperiod; identifying the scheduled date of an issued ticket for selectedpurchasers; adding the aging period to the scheduled date and if thescheduled date plus the aging period is earlier than the current date,determining whether the ticket has been used. If the ticket has not beenused, the system identifies the ticket as an unused ticket and separatesnon-refundable tickets from the list. The system (or a customer servicetool) then calculates the redemption value of the unused ticket. Thesystem submits a report of unused tickets to a client travel agencyand/or a client to notify them of the unused tickets. The client travelagency then processes a refund of the unused ticket. The tickets in thevarious embodiments may be a paper ticket and/or an electronic ticket.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a flow chart illustrating a method and system in accordancewith the invention for facilitating redemption of unused tickets;

FIGS. 2-5 are flow charts illustrating, in more detail, particularembodiments of the process illustrated in FIG. 1; and,

FIG. 6 is a flow chart illustrating a method for submitting a refundreport to an issuing agency to facilitate the issuing agency obtaining arefund.

DETAILED DESCRIPTION

FIG. 1 is a flow chart illustrating, at a high level, one embodiment ofthe ticket tracking and redeeming system and method 10 in accordancewith the invention. In describing the invention, reference will be madeto a system and method for facilitating timely use of electronic ticketsand/or redemption of unused electronic tickets, but the invention is notlimited to these illustrative embodiments. The reminder and redemptionsystem and method are applicable to other types of airline tickets,other types of travel, and to other ticketed endeavors. Further, theinvention is illustrated with reference to services provided by a travelagency to a plurality of its clients. The clients can be individualtravelers or businesses having employees that are frequent travelers.The invention, however, is not limited to such a travel agency or such aclient. Further, wherever this description refers to the communicationof information to a client, it is contemplated that the recipient of theinformation may be a ticket reservation system, a point of sale office,a global distribution system, the ticket holder, a party financiallyrelated to the ticket holder, or any other client of the system.

In an exemplary embodiment, the system may be configured as a dataprocessing system that includes a processor for processing digital data,one or more memory coupled to the processor for storing digital data,and means, coupled to the one or more memory, for inputting digitaldata. In one embodiment, a redemption manager may be configured as anapplication program, may be stored in the memory, and may be accessibleby the processor for directing processing of digital data by theprocessor.

In accordance with a preferred embodiment, the system includes adatabase 12 which includes all travel related activities scheduled andticketed by the travel agency. In addition, a second database 14includes a listing of all clients that subscribe to the redemptionmanagement system. The two databases 12, 14 can, of course, be combinedas a single database including all of the information contained in thetwo separate databases.

The system may include a host server or other computing systemsincluding a processor for processing digital data, a memory coupled tothe processor for storing digital data, an input digitizer coupled tothe processor for inputting digital data, an application program, suchas the redemption manager described above, stored in the memory andaccessible by the processor for directing processing of digital data bythe processor, a display coupled to the processor and memory fordisplaying information derived from digital data processed by theprocessor and a plurality of databases, that may include client data,ticket data, event data and/or like data that could be used inassociation with the present invention. As those skilled in the art willappreciate, each computer will typically include an operating system(e.g., Windows NT, 95/98/2000, Linux, Solaris, etc.) as well as variousconventional support software and drivers typically associated withcomputers. The computers can be in a home or business environment withaccess to a network. In an exemplary embodiment, access may be hadthrough the Internet through a commercially-available web-browsersoftware package.

Each participant may be equipped with a computing system to facilitateonline commerce transactions. The client has a computing unit in theform of a personal computer, although other types of computing units maybe used including laptops, notebooks, hand held computers, set-topboxes, and the like. The point of sale office has a computing unitimplemented in the form of a computer-server, although otherimplementations are possible. The central reservation center has acomputing center in the form of a main frame computer. However, thecentral reservation center may be implemented in other forms, such as amini-computer, a PC server, a network set of computers, and the like.

Communication between the parties to the ticket redemption transactionand the system of the present invention may be accomplished through anysuitable communication means, such as, for example, a telephone network,Intranet, Internet, point of interaction device (point of sale device,personal digital assistant, cellular phone, kiosk, etc.), onlinecommunications, off-line communications, wireless communications, and/orthe like. One skilled in the art will also appreciate that, for securityreasons, any databases, systems, or components of the present inventionmay consist of any combination of databases or components at a singlelocation or at multiple locations, wherein each database or systemincludes any of various suitable security features, such as firewalls,access codes, encryption, de-encryption, compression, decompression,and/or the like.

The presentation of a reminders to use or redeem a ticket or of certainredemption offers and the conduct of some redemption transactions maynecessitate communication between the various institutions such astravel agencies, financial institutions, and service providers. Thecomputers of the various parties may be interconnected via a secondnetwork, referred to as a redemption network. The redemption networkrepresents existing proprietary networks that presently accommodateelectronic transactions. The redemption network may be a closed networkthat is assumed to be secure from eavesdroppers. Examples of theredemption network include the American Express®, VisaNet® and theVeriphone® network.

The computing units may be connected with each other via a datacommunication network that may be a public network and that may beassumed to be insecure and open to eavesdroppers. In an exemplaryembodiment, the network may be embodied as the internet. In thiscontext, the computers may or may not be connected to the internet atall times. For instance, a client or point of sale computer may employ amodem to occasionally connect to the internet, whereas the redemptionmanager computing center or the global reservation system computer mightmaintain a permanent connection to the internet. Specific informationrelated to the protocols, standards, and application software utilizedin connection with the Internet may not be discussed herein. For furtherinformation regarding such details, see, for example, Dilip Naik,“Internet Standards and Protocols” (1998); “Java 2 Complete”, variousauthors, (Sybex 1999); Deborah Ray and Eric Ray, “Mastering HTML 4.0”(1997); Loshin, “TCP/IP Clearly Explained” (1997). All of these textsare hereby incorporated by reference.

The systems may be suitably coupled to network via data links. A varietyof conventional communications media and protocols may be used for datalinks. Such as, for example, a connection to an Internet ServiceProvider (ISP) over the local loop as is typically used in connectionwith standard modem communication, cable modem, Dish networks, ISDN,Digital Subscriber Line (DSL), or various wireless communicationmethods. Client systems might also reside within a local area network(LAN) which interfaces to network via a leased line (T1, D3, etc.). Suchcommunication methods are well known in the art, and are covered in avariety of standard texts. See, e.g., Gilbert Held, “Understanding DataCommunications” (1996), hereby incorporated by reference.

The redemption system and its functional elements may be implemented anddistributed among the various parties. In an exemplary implementation,the redemption network may be implemented as computer software modulesloaded onto the various computer systems of some of the parties, e.g.,the point of sale office and the central reservation center, so that thecomputers of the other parties, e.g., the clients, do not require anyadditional software to participate in the redemption transactionssupported by the redemption system.

The databases discussed herein may be any type of database, such asrelational, hierarchical, object-oriented, and/or the like. Commondatabase products that may be used to implement the databases includeDB2 by IBM (White Plains, N.Y.), any of the database products availablefrom Oracle Corporation (Redwood Shores, Calif.), Microsoft Access orMSSQL by Microsoft Corporation (Redmond, Wash.), or any other databaseproduct. The database may be organized in any suitable manner, includingas data tables or lookup tables. Association of certain data may beaccomplished through any data association technique known and practicedin the art. For example, the association may be accomplished eithermanually or automatically. Automatic association techniques may include,for example, a database search, a database merge, GREP, AGREP, SQL,and/or the like. The association step may be accomplished by a databasemerge function, for example, using a “key field” in each of themanufacturer and retailer data tables. A “key field” partitions thedatabase according to the high-level class of objects defined by the keyfield. For example, a certain class may be designated as a key field inboth the first data table and the second data table, and the two datatables may then be merged on the basis of the class data in the keyfield. In this embodiment, the data corresponding to the key field ineach of the merged data tables is preferably the same. However, datatables having similar, though not identical, data in the key fields mayalso be merged by using AGREP, for example.

The computer may provide a suitable website or other Internet-basedgraphical user interface which is accessible by users. In oneembodiment, the Internet Information Server, Microsoft TransactionServer, and Microsoft SQL Server, are used in conjunction with theMicrosoft operating system, Microsoft NT and Microsoft Windows 2000 webserver software, a Microsoft SQL database system, and a MicrosoftCommerce Server. Additionally, components such as Access or SQL Server,Oracle, Sybase, Informix MySQL, Intervase, etc., may be used to providean ADO-compliant database management system. The term “webpage” as it isused herein is not meant to limit the type of documents and applicationsthat might be used to interact with the user. For example, a typicalwebsite might include, in addition to standard HTML documents, variousforms, Java applets, Javascript, active server pages (ASP), commongateway interface scripts (CGI), extensible markup language (XML),dynamic HTML, cascading style sheets (CSS), helper applications,plug-ins, and the like.

The redemption process starts, at step 16, by identifying a client thathas subscribed to the redemption management system. The client isidentified by accessing the data in database 14. The step of identifyinga client is carried out by computer 11 using a standard software searchroutine. In this and other steps in accordance with the invention, acomputer 11 is identified as the operative instrument for carrying outthe step. In accordance with a preferred embodiment of the invention,all steps in the process are carried out on a centralized computer thathas access to all of the relevant data bases. Alternatively, thefunctions carried out by computer 11 can be carried out by a pluralityof local computers, preferably localized computers that are linkedtogether. The client next determines an aging criteria at step 18. Theaging criteria, for example, may be a period of time ranging frompositive or negative zero to three hundred and sixty five days. Theaging criteria is set by the client and establishes a criteria fordetermining how old a ticket must be before it is assumed that ticketwill not be used. A negative aging period may be used to schedule areminder notice regarding the use or redemption of a ticket prior to thescheduled date of the ticket. Usually the aging criteria is set atbetween about fifteen days and about sixty days. The aging criteria setby a client can be stored in client database 14.

In step 20 all data from database 12 is selected that relates to theparticular client and to tickets for which the final departure date onthe ticket precedes or exceeds the current date by a period of timegreater than the aging period selected by the client. For example, ifthe client has selected an aging period of thirty days, all ticketsissued to the client having a final scheduled departure date more thanthirty days prior to the current date are selected. For convenience,such tickets will hereinafter be referred to as “aged tickets.” Anadvantage of the process in accordance with the invention is that when aclient subscribes to the redemption process, the process can be appliedto all ticket activity carried out by that client with the travel agencyfor some period of time prior to subscribing. For example, the processcan be applied to all activity by that client during any of the previoustime period for which the agency retains such records without manualsupport from the agency. Reference above is made to the “final”departure date because tickets may include several departure dates. Forexample, a ticket may include a departure date for each of the varioussegments of a trip.

At step 21 the information concerning the aged tickets is entered intoan invoice table 22 which keeps all data on such aged tickets and, aswill be explained later, on unused tickets. The redemption system inaccordance with the invention also uses data stored in one of thecentral reservation system (CRS) databases 24. There are several centralreservation system databases available. These databases are maintainedby the airline industry and are accessible by any travel agent. Database24 includes information on all issued tickets. Whenever a ticket isissued for any flight, that information is stored in the centralreservation system database. It is important that much of this sameinformation is also stored in agency database 12 because the airlinesdelete records, usually within seven days, following the date the ticketis used, or when the ticket passes an expiration date. For most airlinesthe expiration date is thirteen months after the ticket date; for someairlines it is twenty four months after the ticket date. The processdescribed herein can be applied to any tickets that have not passed theexpiration date as long as the relevant information is stored in theagency database 12. That is, the process in accordance with theinvention can be applied to any ticket issued in the last thirteenmonths (or twenty four months with some airlines). Without having therelevant information in the agency database, if no record for aparticular ticket was found in the CRS database, it would not bepossible to determine whether that ticket had been used or whether ithad passed its expiration date.

The redemption process continues with step 26, in which the ticketinformation (e.g., electronic ticket information) retrieved from thecentral reservation system database 24 is parsed. Step 26 will beexplained in more detail below, but, in summary, step 26 includes usingthe information from the central reservation system and from the invoicetable to determine whether a particular ticket has been used or not, andif the ticket is an unused, aged ticket, to determine whether the ticketis redeemable or not, and to determine the residual value of thatticket.

The redemption process continues with step 28 in which the residualvalue of an unused and aged ticket is calculated. Step 28 will beexplained in more detail below, but, in summary, includes using theticket information retrieved and then parsed from the centralreservation system database, the invoice table 22, and additionallyinformation stored in yet another database, flight database 30. Flightdatabase 30 holds information on particular flights, including theflight number, cost of the ticket, departure city and arrival city,departure date, and any information on whether and to what extent theticket is redeemable. If redeemable, the amount of redemption credit,i.e., exchangeable value, is calculated as being the residual value ofthe ticket less any fees, penalties, and the like that assessed to theticket holder such as fees for changing an itinerary or for facilitatingredemption of the ticket.

The next step in the process, in accordance with the invention, step 32,is to issue, or offer to issue, redemption credit to the client. Again,this step will be explained in more detail below. In summary, the stepof issuing, or offering to issue, redemption credit, besides issuing acredit to the client, includes updating the central reservation systemdatabase 24, or whatever other database the client desires, the client'spoint of sale office, if desired, and the invoice table.

In accordance with one embodiment of the invention, the redemptionprocess 10 concludes with the step of sending notification of theredemption credit to the traveler, step 34. As mentioned above, inconnection with the issuance of the redemption credit, one or moreoffers may be presented to the client whereby an alternative ticket, adiscounted alternative ticket, or another form of value may be offeredto be provided in exchange for, or in lieu of, the redemption credit.

In an alternative embodiment, as mentioned above in conjunction with thesetting of the aging period, a reminder period may be prescribed and/orcalculated to establish time-based criteria according to which areminder message may be sent to the traveler or the traveler's agentreminding the traveler to timely use or redeem the ticket, step 31. Inaccordance with this embodiment, the reminder period is subtracted fromthe scheduled date of the ticket to determine a reminder date. If thecurrent date is greater than the reminder date, a reminder message maybe sent to the traveler or the traveler's agent reminding the travelerto use or redeem the ticket. In addition to the reminder, variousmethods of redeeming the ticket may be determined based on theassociated timing and the various rules that may be associated with theticket. For example, full refunds may be available only up to a certaindate such as the scheduled date of the ticket. In such cases, anadditional reminder may be sent to the traveler indicating suchinformation. Other criteria may include a diminishing redemption valueas a function of time. Additional reminders may be configured to conveysuch information and to be scheduled in accordance with suchinformation.

In an exemplary embodiment, logical limits may also be implemented suchthat the presentation of information and/or the issuance of redemptioncredit may be made to depend upon the relationship between the amount ofavailable redemption credit and the predetermined limit. In accordancewith this embodiment, a client may designate one or more limitingvalues, which may be associated with a logical definition of how thelimiting value is to be applied. For example, a client may specify abenchmark value to be used to prevent or discard redemption offers thatdo not satisfy (e.g., meet or exceed) the benchmark criteria (e.g., bysetting the benchmark at $200 and defining the benchmark so as to causeit to be treated as a logical minimum, a client may avoid receivingoffers for redemption credit in quantities lower than $200). Thebenchmark value may therefore be chosen so as to limit the quantityand/or magnitude of offers to be presented to a client. This feature maybe useful, for example, wherever a client desires to receive only offerswhere the value to be captured exceeds the costs of conducting theredemption transaction. In another exemplary embodiment, a client mayspecify a benchmark and define it as a logical minimum level above whichredemption offers must be presented to an alternative party or must behandled in an alternative manner. Accordingly, once the amount ofredemption credit has been determined, the system may determine whetherthat amount satisfies the predetermined benchmark criteria. Further, thesystem may be configured to track the quantity of tickets havingredemption values that satisfy, or fail to satisfy, the benchmarkcriteria and to report such information to a designated party such asthe client or another interested party.

Where the determination of residual value or redemption credit isdifficult or impossible to automatically determine, the system may beconfigured to transmit appropriate information to a customer servicetool. The customer service tool may then be used to facilitatedetermination of residual value through an alternative method such asmanual input. Then, the customer service tool may transmit that value tothe system.

FIGS. 2-5 illustrate, in flow chart form, aspects of various embodimentsof the invention in greater detail. FIG. 2 illustrates in more detail,for example, step 26 of the parsing of the ticket (e.g., electronicticket) information retrieved from the central reservation database. Asexplained above, the redemption method in accordance with the inventionis practiced by implementing various process steps on a computer 11.Computer 11 is preferably a centralized computer controlling and/orinterfacing with each of the various databases, but alternatively can bea plurality of individual personal computers or the like. Throughout theillustrative figures, computer 11 will be illustrated as a singlecentralized computer. As such, computer 11 performs the various methodsteps by appropriately interfacing with the databases that comprise thetotal system.

Step 26 of the redemption method starts by connecting computer 11 to thecentral reservation system database 24, step 37. Similarly, computer 11connects to invoice table 22 and retrieves information from the table,step 39, concerning a particular passenger and a particular invoice fora ticket judged to be an aged ticket. The invoice may include multipleflights or multiple flight segments for that particular passenger.Information is also retrieved from central reservation system database24 concerning each of those flights and flight segments to determinewhich portion of the invoice has been used.

In step 40 the electronic ticket record (ETR) is viewed and adetermination is made by software resident in computer 11 as to whatticket segments were used, what fare was paid for those ticket segments,and whether the ticket is redeemable or not. The information necessaryfor carrying out step 40 is found in the central reservation system database 24.

In step 42 the information retrieved in step 40 is parsed and flightdatabase 30 is updated to reflect the information retrieved from thecentral reservation system database. As part of step 42 a determinationis made as to the last open segment of any of the scheduled flights thatwere ticketed. This reflects the fact that a portion of the ticket mayhave been used while other segments were not used. In addition, thetraveler may have revised the ticket to change the scheduled time. Thatinformation would be found in the central reservation system database,but might not be reflected in the invoice table or flight database.Flight database 30 is updated with the revised open segment information.

In step 44 the updated information on the date of the last open segmentis compared to the current date to determine whether that date hasexceeded the aging period. If not, for example because the traveler hasrevised the scheduled departure dates, the invoice table is updated withthe revised last scheduled open segment date, step 45, and the processis terminated with respect to that particular traveler or invoice. Uponsuch termination, the process returns to step 39 and retrieves anotherinvoice record. If the last open segment departure date is past theaging period, the residual value of the ticket or ticket segment isdetermined at step 46. This information is used to update both theflight database and the invoice table. In accordance with one embodimentof the invention, the next step in the process, step 48, is to retrievedelivery information. This information, includes, for example, theaddress and/or fax number for the scheduled traveler. This informationis retrieved from the ticketing database 12 (not illustrated in thisfigure), invoice table 22, or flight database 30. In step 50 adetermination is made as to whether the ticket or ticket segment isredeemable. This determination is a compilation of information stored inthe flight database concerning the original nature of the ticket plusinformation from the central reservation system database concerningwhether the ticket was used or not. The information so determined isused to update both the flight database 30 and the invoice table 22.Following the updating of invoice table 22, either after step 50 orafter step 45, the process continues with the step of calculating theresidual value, step 28. Optionally, the process also continues by path52, by returning to step 39 and repeating the process for an additionalinvoice record for the same client.

FIG. 3 illustrates, in more detail, aspects of various embodiments ofmethod step 28, calculating the residual value. The step of calculatingthe residual value starts by retrieving information from the invoicetable 22, step 52. Again, the method steps illustrated in FIG. 3 arecarried out by computer 11 which can be either a centralized computer ora plurality of distributed computers. Based on the information in theinvoice table and in the central reservation system database 24, adetermination is made at step 54 of whether the ticket or ticket segmenthas been fully used. Based on the determination of whether the tickethas been fully used or not, a further determination is made at step 55as to whether, and to what extent and under what conditions, the ticketis refundable or redeemable for value. Depending on the contract termsentered into when the ticket was issued, some tickets may not berefundable or redeemable if any portion of the ticket has been used.Further contract terms may apply if part of the ticket has been used. Ifthe ticket is at least partially refundable, a refund may be issued. Ifthe ticket is fully redeemable, the amount of redemption credit isdetermined to be, in accordance with step 56, the residual valuecalculated in step 46. If the ticket or ticket segment is not fullyredeemable, a determination is first made at step 57 as to whether theremaining portion of the ticket is a valid partial. That is, adetermination is made as to whether the partial ticket is redeemable ifsome other portion of the ticket has been used. This determination ismade based on information stored in the flight database 30. If theremaining portion is determined to be a valid portion, the amount ofpartial redemption credit is calculated in step 58. The amountcalculated in step 58 is dependent on information retrieved from theflight database 30 and invoice table 22. Flight database 30 includesinformation concerning fees and penalties that may be assessed in theevent a ticket is changed, canceled, partially used, or not used at all.This information is used in calculating the amount of the partialredemption credit. The amount of redemption credit, step 59, isdetermined to be the amount so calculated. The amount determined insteps 58 and 59 is used to update invoice table 22. After determiningthe amount of redemption credit in either step 56 or step 59, a finaldetermination is made at step 61 as to whether there are any additionalpenalties, fees or other considerations to affect the amount ofredemption credit. If the ticket is determined to be non-redeemable, atstep 61 the status of the ticket is set to non-redeemable in the invoicetable and the process is terminated with respect to this record. If theticket is determined at step 61 to be redeemable, the process continuesto step 32 and information is communicated to designated parties so thata redemption offer may be presented and redemption may be facilitated.

FIG. 4 illustrates, in accordance with various embodiments of theinvention, facilitating redemption step 32 in more detail. Following thecompletion of step 28, computer 11 again connects to the centralreservation system database in step 70. The step of facilitatingredemption is closely connected to central reservation system database24 because, in general, the process of facilitating redemption requiresan involved process in which the electronic ticket is returned to theairline. As part of a checks and balances system, a coupon is printedindicating the return of the ticket; at a later time the returned-ticketcoupon can be matched up with the airline records of the ticket forwhich redemption credit was granted. In accordance with an embodiment ofthe invention, computer 11 signs into a ticket printer in step 72.Again, this is done interactively with the central reservation systemdatabase. Computer 11 then retrieves the record of the transaction fromthe invoice table at step 74. If the ticket in question is redeemableand has not been used, that information is conveyed to database 24 atstep 76. A coupon is then queued to print at step 78. Printing occurs atthe end of the process for a particular traveler, as described below.Following the queuing of the coupon, the passenger name record for theparticular ticketed passenger is updated, step 80, in database 24.Again, steps 76, 78, and 80 are all interactive with a centralreservation database. If computer 11 determines from the invoice tablethat the ticket in question is not redeemable, the ticket status forthis transaction is set to show that the ticket is non-redeemable instep 82. The invoice table is updated to reflect this status. In step 84computer 11 determines, at the completion of either step 80 or step 82whether any redemption credit remains for this passenger name record. Ifthere are additional redemption credit issues remaining for thispassenger name record, the process returns to step 74 and the nextinvoice record for this client is processed. If there are no furtherredemption credits to be processed for this passenger name record, thecoupons in the queue are printed, step 85, and the process continues, inaccordance with one embodiment, with step 34.

In accordance with one embodiment of the invention, as illustrated inFIG. 5, following the step of issuing redemption credit, step 32,notification is sent to the passenger in step 34. Computer 11 againinterfaces with invoice table 22 to retrieve the record of thistransaction and to get the delivery information generated in step 48.This is done in step 90. Based on the record retrieved in step 90,computer 11 makes a determination, in step 91, as to the status of thistransaction, either redeemable or non-redeemable. If the status isdetermined to be redeemable, a form is selected in step 92 for aredeemable transaction. If the transaction is determined to benon-redeemable, a form is selected in step 96 for a non-redeemabletransaction. The form selected in either step 92 or 96 is typed in step98 and then is sent by facsimile in step 100 to the ticketed traveler orsent by e-mail to the ticketed traveler in step 102. Upon notificationof the traveler, the process is completed, at step 104, for thistraveler. The process can now be repeated for other travelers or forother clients.

Furthermore, as discussed above, if a traveler purchases a ticket froman issuing agency (e.g., travel agent), according to ARC restrictions,any refund related to the ticket must be issued by the same issuingagency. Accordingly, when a traveler purchases a ticket from an issuingagency, but the traveler uses an unrelated financial transaction account(e.g., charge card), the traveler is not able to obtain a refunddirectly from the host of the transaction account. As such, in anotherembodiment of the present invention, to facilitate the issuing agencyobtaining a refund, the system collects ticket data from a financialtransaction account (e.g., charge card account), transmits the ticketdata to a search engine which uses the ticket data to find open ticketsand which determines the value of the open tickets, then transmits areport of the open tickets and value to the issuing agency.

More particularly, with respect to FIG. 6, the system acquires ticketdata from a financial transaction account (step 605). In one embodiment,the ticket information is retrieved from the transaction account Mlfiles. The ticket data may include, for example, traveler name, bookingpseudo city, ticketing pseudo city, IATA code, passenger name record(PNR), date of purchase, amount of purchase, issuing agency where theticket was purchased and/or any other data related to the ticket. Thesystem then transmits the ticket data to a search engine such as, forexample, NetEdge Harvester®. In one embodiment, the search engine may belocated on, or operate on, the issuing agency system. The search enginenext uses the ticket data to find open tickets (step 610). The searchengine may find open tickets in a similar manner as discussed herein.For example, the search engine may find open tickets by setting an agingperiod; identifying the scheduled date of an issued ticket for selectedpurchasers; adding the aging period to the scheduled date and if thescheduled date plus the aging period is earlier than the current date,determining whether the ticket has been used. If the resulting tickethas not been used, the system identifies the ticket as an unused ticketand separates non-refundable tickets from the list (step 615). Thesystem (or a customer service tool) then calculates the redemption valueof the unused tickets (step 620). The system then constructs a report orsimilar list of unused tickets, along with the respective redemptionvalue of the tickets (step 625). The system then submits a report ofunused tickets to a client travel agency and/or a client to notify themof the unused tickets (step 630). The client travel agency thenprocesses a refund of the unused ticket by any method known in the art.As discussed herein, the tickets in this and other embodiments may be anelectronic ticket, but in alternative embodiments, a paper ticket or anyother access ticket, account or token may be used.

Thus it is apparent that there has been provided, in accordance with theinvention, a redemption credit system and method that fully meet theneeds specified above. Although the system and method have beendescribed and illustrated with reference to specific illustrativeembodiments, it is not intended that the invention be limited to theseillustrative embodiments. Those skilled in the art will recognize thatmany variations and modifications to these illustrative embodiments arepossible without departing from the spirit and scope of the appendedclaims. For example, as noted above, the databases that have beenreferred to can be individual databases, a single central database, ordatabases partitioned in ways other than as illustrated in the figures.Preferably the invention is practiced through use of a single centralcomputer which can contain all transactions for a particular client,regardless of location of that client or various departments, divisionsor other segments of that client. Additionally, the invention has beenillustrated with reference to particular practices presently in use bythe airline industry. Those of skill in the art will recognize that theairline industry periodically changes its practices, procedures, andrequirements, and the invention is not to be limited to any oneparticular set of airline requirements. Further, although illustratedwith reference to electronic tickets used in the airline industry, theinvention is applicable to other forms of ticketing in the airlineindustry, in other modes of transportation, and other ticketedactivities.

It will be appreciated, that many applications of the present inventioncould be formulated. One skilled in the art will appreciate that thenetwork may include any system for exchanging data or transactingbusiness, such as the Internet, an intranet, an extranet, WAN, LAN,satellite communications, and/or the like. It is noted that the networkmay be implemented as other types of networks, such as an interactivetelevision (ITV) network. The users may interact with the system via anyinput device such as a keyboard, mouse, kiosk, personal digitalassistant, handheld computer (e.g., Palm Pilot®), cellular phone and/orthe like. Similarly, the invention could be used in conjunction with anytype of personal computer, network computer, workstation, minicomputer,mainframe, or the like running any operating system such as any versionof Windows, Windows NT, Windows2000, Windows 98, Windows 95, MacOS,OS/2, BeOS, Linux, UNIX, Solaris or the like. Moreover, although theinvention is frequently described herein as being implemented withTCP/IP communications protocols, it will be readily understood that theinvention could also be implemented using IPX, Appletalk, IP-6, NetBIOS,OSI or any number of existing or future protocols. Moreover, the systemcontemplates the use, sale or distribution of any goods, services orinformation over any network having similar functionality describedherein.

It should be appreciated that the particular implementations shown anddescribed herein are illustrative of the invention and its best mode andare not intended to otherwise limit the scope of the present inventionin any way. Indeed, for the sake of brevity, conventional datanetworking, application development and other functional aspects of thesystems (and components of the individual operating components of thesystems) may not be described in detail herein. Furthermore, theconnecting lines shown in the various figures contained herein areintended to represent exemplary functional relationships and/or physicalcouplings between the various elements. It should be noted that manyalternative or additional functional relationships or physicalconnections may be present in a practical electronic transaction system.

As will be appreciated by one of ordinary skill in the art, the presentinvention may be embodied as a method, a data processing system, adevice for data processing, and/or a computer program product.Accordingly, the present invention may take the form of an entirelysoftware embodiment, an entirely hardware embodiment, or an embodimentcombining aspects of both software and hardware. Furthermore, thepresent invention may take the form of a computer program product on acomputer-readable storage medium having computer-readable program codemeans embodied in the storage medium. Any suitable computer-readablestorage medium may be utilized, including hard disks, CD-ROM, opticalstorage devices, magnetic storage devices, and/or the like.

The present invention may be described herein in terms of functionalblock components, screen shots, optional selections, various processingsteps, block diagrams and flowchart illustrations of methods, apparatus(e.g., systems), and computer program products according to variousaspects of the invention. It should be appreciated that such functionalblocks may be realized by any number of hardware and/or softwarecomponents configured to perform the specified functions. For example,the present invention may employ various integrated circuit components,e.g., memory elements, processing elements, logic elements, look-uptables, and the like, which may carry out a variety of functions underthe control of one or more microprocessors or other control devices. Itwill further be understood that each functional block of the blockdiagrams and the flowchart illustrations, and combinations of functionalblocks in the block diagrams and flowchart illustrations, respectively,can be implemented by computer program instructions. These computerprogram instructions may be loaded onto a general purpose computer,special purpose computer, or other programmable data processingapparatus to produce a machine, such that the instructions which executeon the computer or other programmable data processing apparatus createmeans for implementing the functions specified in the flowchart block orblocks.

The software elements of the present invention may be implemented withany programming or scripting language such as C, C++, Java, COBOL,assembler, PERL, Visual Basic, SQL Stored Procedures, extensible markuplanguage (XML), with the various algorithms being implemented with anycombination of data structures, objects, processes, routines or otherprogramming elements. These computer program instructions may also bestored in a computer-readable memory that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including instruction meanswhich implement the function specified in the flowchart block or blocks.The computer program instructions may also be loaded onto a computer orother programmable data processing apparatus to cause a series ofoperational steps to be performed on the computer or other programmableapparatus to produce a computer-implemented process such that theinstructions which execute on the computer or other programmableapparatus provide steps for implementing the functions specified in theflowchart block or blocks.

Accordingly, functional blocks of the block diagrams and flowchartillustrations support combinations of means for performing the specifiedfunctions, combinations of steps for performing the specified functions,and program instruction means for performing the specified functions. Itwill also be understood that each functional block of the block diagramsand flowchart illustrations, and combinations of functional blocks inthe block diagrams and flowchart illustrations, can be implemented byeither special purpose hardware-based computer systems which perform thespecified functions or steps, or suitable combinations of specialpurpose hardware and computer instructions.

Further, it should be noted that the present invention may employ anynumber of conventional techniques for data transmission, signaling, dataprocessing, network control, and the like. Still further, the inventioncould be used to detect or prevent security issues with a client-sidescripting language, such as JavaScript, VBScript or the like. For abasic introduction of cryptography and network security, the followingmay be helpful references: (1) “Applied Cryptography: Protocols,Algorithms, And Source Code In C,” by Bruce Schneier, published by JohnWiley & Sons (second edition, 1996); (2) “Java Cryptography” by JonathanKnudson, published by O'Reilly & Associates (1998); (3) “Cryptography &Network Security: Principles & Practice” by William Stalling, publishedby Prentice Hall; all of which are hereby incorporated by reference.

In the foregoing specification, the invention has been described withreference to specific embodiments. However, it will be appreciated thatvarious modifications and changes can be made without departing from thescope of the present invention. The specification and figures are to beregarded in an illustrative manner, rather than a restrictive one, andall such modifications are intended to be included within the scope ofpresent invention. For example, the steps recited in any of the methodor process descriptions may be executed in any order and are not limitedto the order presented.

Benefits, other advantages, and solutions to problems have beendescribed above with regard to specific embodiments. However, thebenefits, advantages, solutions to problems, and any element(s) that maycause any benefit, advantage, or solution to occur or become morepronounced are not to be construed as critical, required, or essentialfeatures. As used herein, the terms “comprises,” “comprising,” or anyother variation thereof, are intended to cover a non-exclusiveinclusion, such that a process, method, article, or apparatus thatcomprises a list of elements does not include only those elements butmay include other elements not expressly listed or inherent to suchprocess, method, article, or apparatus. Further, no element describedherein is required for the practice of the invention unless expresslydescribed as “essential” or “critical.”

1. A computer-implemented method for facilitating an automatedredemption of an unused ticket, comprising steps of: setting, via acomputer system, an aging period; identifying, via a computer system, ascheduled date of an issued ticket; adding, via a computer system, theaging period to the scheduled date; determining, via a computer system,at the scheduled date plus the aging period whether all or a portion ofthe issued ticket is unused; if all or a portion of the ticket has notbeen used, identifying, via a computer system, the issued ticket as anunused ticket and setting a ticket status field in a table; comparing,via a computer system, information in an invoice table and a centralreservation system database to determine at least one of a use of theticket and a change to the ticket; calculating, via a computer system, aresidual value of the ticket based on a contract term associated withthe ticket and any changes to the ticket or partial use of the ticket;storing, via a computer system, the residual value in the invoice table;comparing, via a computer system, the residual value to a minimumthreshold for presenting a ticket redemption offer to a client;generating, via a computer system, a report based at least in part onthe table and the comparing the residual value step; and transmitting,via a computer system, the report to at least one of a client travelagency and a client of the unused ticket.
 2. The method of claim 1,further comprising a step of processing, by the client travel agency, arefund of the unused ticket.
 3. The method of claim 1, furthercomprising a step of collecting ticket data from a financial transactionaccount, wherein the ticket data is used to determine an issued ticketfor any of a plurality of selected purchasers.
 4. The method of claim 1,wherein the ticket is at least one of a paper ticket and an electronicticket.
 5. The method of claim 1, further comprising a step ofseparating non-refundable tickets.
 6. The method of claim 1, wherein theticket is an electronic ticket that includes a plurality of data fields,and wherein the step of calculating further includes communicating theplurality of data fields to a customer service tool and receiving theresidual value from the customer service tool.
 7. The method of claim 1,wherein the step of identifying, via a computer system, a scheduled dateof an issued ticket, is based upon an analysis of at least one of aclient travel agency database and a global distribution system.
 8. Themethod of claim 1, wherein the ticket corresponds to any of a pluralityof selected purchasers.
 9. The method of claim 1, further comprising:collecting said scheduled date of said issued ticket and identifyingwhether said issued ticket has been used using a plurality of centralreservation system databases.
 10. A computer readable storage mediumhaving stored thereon a plurality of instructions, said plurality ofinstructions when executed by one or more processors, cause said one ormore processors to perform: setting an aging period; identifying ascheduled date of an issued ticket; adding the aging period to thescheduled date; determining at the scheduled date plus the aging periodwhether all or a portion of the issued ticket is unused; if all or aportion of the ticket has not been used, identifying the issued ticketas an unused ticket and setting a ticket status field in a table;comparing information in an invoice table and a central reservationsystem database to determine at least one of a use of the ticket and achange to the ticket; calculating a residual value of the ticket basedon a contract term associated with the ticket and any changes to theticket or partial use of the ticket; storing the residual value in theinvoice table; comparing the residual value to a minimum threshold forpresenting a ticket redemption offer to a client; generating a reportbased at least in part on the table and the comparing the residual valuestep; and transmitting the report to at least one of a client travelagency and a client of the unused ticket.
 11. The method of claim 1,wherein a third party issuing agency is notified that the unused ticketwas purchased with a charge card.
 12. A computer readable mediumaccording to claim 10 wherein a third party issuing agency is notifiedthat the unused ticket was purchased with a charge card.
 13. A computerreadable medium according to claim 10 further comprising instructionsfor executing the step of collecting said scheduled date of said issuedticket and identifying whether said issued ticket has been used using aplurality of central reservation system databases.
 14. The method ofclaim 1, wherein the ticket redemption offer includes at least one of analternative ticket, a discounted alternative ticket, and a form of valueoffered to be provided in exchange for, or in lieu of, a redemptioncredit.
 15. The method of claim 1, wherein the ticket redemption offeris a redemption credit.
 16. A computer readable storage medium accordingto claim 10, wherein the ticket redemption offer includes at least oneof an alternative ticket, a discounted alternative ticket, and anotherform of value offered to be provided in exchange for, or in lieu of, aredemption credit.
 17. A computer readable storage medium according toclaim 10, wherein the ticket redemption offer is a redemption credit.